Important: If no further configuration is needed, proceed to Preparing and Using the Client Workstation chapter of this guide for information and instructions for preparing and using WEM Clients.
Important: Unless otherwise specified, all information in this chapter applies to both Sun Solaris- and Red Hat Enterprise Linux-based WEM systems.|
Refer to the Controlling Server Component Processes section later in this chapter for more information.
|
|
|
Refer to Preparing and Using the Client Workstation chapter of this guide for more information.
|
|
|
Refer to Preparing and Using the Client Workstation chapter of this guide for more information.
|
|
|
Refer to the Controlling Server Component Processes section later in this chapter for more information.
|
|
|
Refer to the Controlling Server Component Processes section later in this chapter for more information.
|
|
|
Refer to WEM Database Maintenance chapter of this guide for more information.
|
|
 Important: Many of these files contain user-configurable parameters for tailoring the operation of the WEM. Information on the various parameters in these files is provided within the files. Refer to the Server Configuration Files section of this chapter for more information. |
|
|
Refer to Enhanced WEM Logging chapter of this guide for more information.
|
|
|
Refer to Enhanced WEM Logging chapter of this guide for more information.
|
|
 Caution: Improper configuration of this file can adversely affect WEM operation. |
|
 Caution: Do not alter this file. |
|
|
Refer to Enhanced WEM Logging chapter of this guide for more information.
|
|
 Important: The NorthBound Server and Notification Service processes are licensed-enabled and are not operational without the appropriate license. Contact your local Cisco sales representative for additional information. |
|
 Important: The NorthBound Server and Notification Service processes are licensed-enabled and are not operational without the appropriate license. Contact your local Cisco sales representative for additional information. |
|
 Important: The NorthBound Server and Notification Service processes are licensed-enabled and are not operational without the appropriate license. Contact your local Cisco sales representative for additional information. |
|
 Caution: Do not alter this file. |
|
|
Refer to Enhanced WEM Logging chapter of this guide for more information.
|
|
 Caution: Do not alter this file. |
|
|
WEM Server SNMP MIB file. Refer to the Cisco ASR 5000 Series SNMP MIB Reference for more information on the objects and alarms defined in the MIB.
|
|
|
Refer to WEM Process Monitor chapter of this guide for more information.
|
|
|
Refer to the Controlling Server Component Processes section later in this chapter for more information.
|
|
 Important: This script should be used with the same EMS releases. It will be required in case of EMS setup migration from one machine to another machine, OS change (Solaris 8 to Solaris 10), etc. There is a config file with this script (ems_migrate.cfg), in which the list of directories for backup and restore can be specified. For example: dir_list=postgres/data server/etc server/bsschema |
|
|
Script used for collecting server logs and other information that is useful for troubleshooting. Refer to the Capturing WEM Server Logs using Script section of the Troubleshooting the WEM appendix of this guide for more information on using this script.
|
As identified in the WEM Server Directory and Important Files table, the WEM provides a number of configuration files which can be modified to fine-tune the operation of the application. These files are located in the /<ems_dir>/server/etc directory by default.
Caution: For most of these files, the WEM application process must be stopped and restarted in order for modifications to take effect. To ensure proper operation, be sure to read and understand all the information provided in the files prior to making changes.
Important: Refer to the WEM Configuration File Parameters appendix for detailed information on the server configuration file parameters.
Caution: To ensure proper operation of the WEM, bulk statistic schema and formatting configuration in this file should not be altered.
Important: Several parameters contained in this file are configurable through the installation process.The bulk statistics data from a managed system is received by the WEM Server in Comma Separated Value (CSV) format. The data is stored in the /server/data/<system-name> directory by default. The XML files should get generated under <server-dir>/xmldata as long as the files are getting parsed and the data is getting logged in database. This generation of XML files is done by a separate process namely, bulkstatserver.
Important: Several parameters contained in this file are configurable through the installation process.
Caution: Improper configuration of this file can adversely affect WEM operation.
Important: Several parameters contained in this file are configurable through the installation process.
Important: The parameter in this file is configurable through the installation process.
Important: The NorthBound Server and Notification Service processes are license-enabled and are not operational without the appropriate license. Please contact your local Cisco sales representative for additional information.
Important: Several parameters contained in this file are configurable through the installation process.This file contains parameters used by the Process Monitor (refer to the WEM Process Monitor chapter for more information) function. These include parameters such as the directories from which WEM-related processes are started, polling intervals, and maximum percentage thresholds.
This file contains parameters for the operation of the PSMon (Process Monitor) function supported by the WEM. Additional details on this function and the parameters in this file are located in the WEM Process Monitor chapter of this guide.
Caution: To ensure proper operation of the WEM, do not edit the parameters in these files.
Caution: To ensure proper operation of the WEM, do not edit the parameters in these files.This file contains parameters pertaining to PostgreSQL database vacuuming. Additional details on this function and the parameters in this file are located in WEM Database Maintenance chapter of this guide.
By default, log files generated by the WEM application are stored in the /<ems_dir>/server/log directory. The location is specified in the xxxxlogger.xml files stored in the /<ems_dir>/server/etc directory (refer to the Enhanced WEM Logging chapter for information on these files).
Within the log directory, subdirectories are created as needed to contain log files for each of the various components that comprise the WEM Server:
The above directory names are appended with a datestamp (YYYYMMDD) and timestamp (HHMMSS). For example, a subdirectory containing EMS Server logs might be named SERVER_LOG_20051230_164433.
Note that logs for the Process Monitor are written to the watchdog.log file in the log base directory.
The WEM provides enhanced logging functionality that allows for the customization of the log file output. More detailed information on configuring and using this functionality can be found in the Enhanced WEM Logging chapter of this guide.
What ever debugging level is configured, the messages with that level and above will be logged in the log file. For example, if level 3 is specified then, all messages of severity Severe, Warning, Info, Config, and Fine appear in the log, however, those messages with a severity of Finer and Finest do not.
The logging level is configurable using the WEM Server executable, serv (located in the /<ems_dir>/server directory by default). The default level is Finest.
Alternatively, the xxxxlogger.xml files stored in the /<ems_dir>/server/etc directory provide a mechanism for specifying the log level for the specific WEM server modules. These levels only take effect if the configured level is more granular than that configured at the server level.
As identified in the WEM Server Directory and Important Files table, a number of user-executable scripts are provided with the WEM. These scripts are located in the /<ems_dir>/server/scripts directory by default.
|
•
|
backup.sh: Used to perform the backup/restore of the WEM databases.
|
|
•
|
batchJob.sh: Uses user-provided information to telnet into a managed device, execute a command, and write its output to a log file. Refer to the README.batchJob.txt file in the same directory for more information.
|
|
•
|
deleteFilesTables.sh: Deletes unnecessary information from database tables and unused files. The tableFile.cfg file is used to specify the criteria for determining which information or files are “unnecessary”. Refer to the README.deleteFilesTables.txt file in the same directory for more information.
|
|
•
|
kill_ems_clnt.sh: Provides a mechanism for terminating specific WEM client sessions. Refer to the README.kill_ems_clnt.txt file in the same directory for more information.
|
|
•
|
loadConfig.sh: Used by the Script Server to load configuration files on the managed systems. This is not a user-executable script.
|
|
•
|
loadRootCron.sh: Used by the Script Server to load the root user’s cron entry for scheduling system configurations as part of the update feature. This is not a user-executable script.
|
|
•
|
set_superuser_password.sh: This script is used to reset the “superuser” password to the default.
|
|
•
|
showCommand.sh: Used by the Script Server to access and execute commands on managed devices. This is not a user-executable script.
|
|
•
|
showsupportdetails.sh: Writes the show support details command output from the specified ASR 5000 to a text file for later processing. Refer to the README.ShowSupportDetails.txt file in the same directory for more information.
|
|
•
|
sortIPPools.sh: Used to fetch the information of IP addresses for a given group in a sorted mail and to sort it out. Refer to the README_sortIPPools.txt file in the same directory for more information.
|
./script_name
Where script_name is the name of the script as identified above.
|
Step 1
|
|
Step 2
|
Go to the server directory within the WEM installation directory by entering the following command:
|
Important: The NorthBound Server and Notification Service processes are license-enabled and are not operational without the appropriate license. Please contact your local Cisco sales representative for additional information.|
Step 1
|
|
Step 1
|
The WEM application and its ancillary components must be stopped in the exact order as listed below.
Important: These instructions assume that the WEM was installed in the default directory, /users/ems.|
Step 1
|
|
Step 2
|
Go to the server directory within the WEM installation directory by entering the following command:
|
|
Step 10
|
|
Step 1
|
|
Step 4
|
|
Step 1
|
|
Step 4
|
|
Step 1
|
|
Step 4
|
